Device self-servicing in an autonomous decentralized peer-to-peer environment

ABSTRACT

An approach, for autonomous self-servicing of decentralized peer-to-peer devices in an autonomous decentralized peer-to-peer telemetry (ADEPT) environment. A first ADEPT peer connects to ADEPT peers based on peer consensus. The first ADEPT peer determines service needs based on receiving diagnostic inputs. The first ADEPT peer identifies service providers based on consensus service contracts associated to the service needs. The first ADEPT peer creates service orders based on the service providers and output the service orders to service providers based on the consensus service contracts.

BACKGROUND OF THE INVENTION

The present invention relates generally to the field of Internet ofThings (IoT) and more particularly, to device self-servicing enablementin an autonomous decentralized peer-to-peer telemetry (ADEPT)environment

An “Internet of Things” (IoT) can be a group of physically tangibleelectronic or computerized “things” that can be capable of networkconnectivity. Examples of IoT devices (e.g., “things”) can compriseenvironmental sensors, mobile devices, motion detectors, securitycameras and “smart” appliances. Further, IoT devices can be equippedwith a plurality of network interfaces, computer processors and localuser interfaces.

IoT sensor devices can collect data through sensors, cameras or othermonitoring techniques and can transmit data continuously, frequently orin response to, an occurrence of a triggering condition, to one or moreremote IoT controllers through a network. IoT devices can performfunctions such as, but not limited to, reporting a status of anappliance, an environmental controller or a motion sensor. IoT devicescan also send instructions to a monitored device in response tomonitored data or in response to instructions received from the IoTcontroller over a network.

IoT controllers are often centralized and perform functions such as, butnot limited to, authentication and registration of IoT devices,messaging, file management, Quality of Service (QoS) coordination andlife cycle management. Different IoT solution vendors can provideproprietary solutions that follow similar centralized architectures andcentralized IoT controllers can be hosted on a cloud environment.

Some centralized IoT solutions can enable extension of some processingto the edge (i.e., edge computing) where edge computing can compriseapplications, data and services received from centralized nodes toenable analytics and knowledge generation at the source of the data, butwhere those resources may not be continuously connected to a network.These described IoT edge services often function as spokes of a cloudcontroller that perform aggregation and regional tasks to have datafurther aggregated and controlled at the central controller. Whilecentral control can be efficient for high-value IoT applications, acentralized model can become expensive to support for a large number(e.g., billions) of low value IoT devices over a long lifecycle (e.g.,years). Additionally, IoT devices on the edge can have increasedcapability and sophistication when IoT devices comprise significantcomputing and memory capability. Sophisticated IoT devices can beleveraged to complement centralized solutions by enabling decentralizedpeer-to-peer networked devices to perform self-service tasks such as,but not limited to, self-diagnosis, predict equipment failure andanticipate service needs.

SUMMARY

As disclosed herein, a method, for autonomous self-servicing ofdecentralized peer-to-peer devices in an autonomous decentralizedpeer-to-peer telemetry (ADEPT) environment, the method comprising:connecting, by a first ADEPT peer, to one or more ADEPT peers based onpeer consensus; determining, by the first ADEPT peer, one or moreservice needs based on receiving one or more diagnostic inputs;identifying, by the first ADEPT peer, one or more service providersbased on one or more consensus service contracts associated to the oneor more service needs; creating, by the first ADEPT peer, one or moreservice orders based on the one or more service providers andoutputting, by the first ADEPT peer, the one or more service orders toone or more service providers based on the one or more consensus servicecontracts. A computer system and a computer program productcorresponding to the above method are also disclosed herein.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is described in the detailed description whichfollows, in reference to the noted plurality of drawings by way ofnon-limiting examples of exemplary embodiments of the present invention.

FIG. 1 depicts a functional block diagram illustrating a computingenvironment, in accordance with an embodiment of the present invention;

FIG. 2 depicts an IoT ADEPT peer autonomous device architecture, inaccordance with an embodiment of the present invention;

FIG. 3 illustrates a flowchart depicting ADEPT peer self-servicinginteractions, in accordance with an embodiment of the present invention;

FIG. 4 depicts a sample implementation of an IoT ADEPT peer deviceoperation, in accordance with an embodiment of the present invention;

FIG. 5 depicts transactions in a sample digital value exchange scenarioof an IoT ADEPT peer device, in accordance with an embodiment of thepresent invention; and

FIG. 6 depicts a block diagram of components of the server and/or thecomputing device, in accordance with an embodiment of the presentinvention.

DETAILED DESCRIPTION

Aspects of the present disclosure and certain features, advantages anddetails thereof, are explained more fully below with reference to thenon-limiting examples illustrated in the accompanying figures.Descriptions of well-known materials, fabrication tools, processingtechniques, etc., are omitted to avoid obscuring the disclosure withunnecessary detail. It should be understood, however, that the detaileddescription and the specific examples, while indicating aspects of theinvention, are given by way of illustration only and not by way oflimitation. Various substitutions, modifications, additions and/orarrangements, within the spirit and/or scope of the underlying inventiveconcepts will be apparent to those skilled in the art from thisdisclosure.

Embodiments of the present invention provide systems, methods, andcomputer program products by which IoT devices can engage in devicecontrolled self-servicing based on foundational IoT trusted transactionsin a peer-to-peer and decentralized manner comprising an AutonomousDecentralized Peer-to-peer Telemetry (ADEPT) architecture. Elements ofembodiments of the present invention can comprise peer-to-peermessaging, distributed file sharing and autonomous device coordinationto enable peer-to-peer trust and negotiate service contracts betweentrading partners (e.g., ADEPT networked devices and service providers).

Peer-to-peer messaging can comprise devices in a network that cancommunicate using peer-to-peer messaging. Depending on the nature ofinteraction and relationship between devices, peer-to-peer messaging cancomprise simple notifications and/or can trigger more complex actionsbetween devices. Example uses of peer-to-peer messaging can comprisefunctions such as, but not limited to, device notification toward anowner/user, device requests toward other devices and remoteauthentication of other network accessible devices (e.g., physicalequipment, service providers).

Distributed file sharing can comprise devices in a network that share arange of files and/or portions of files using one or more connecteddevices. File sharing protocols such as, but not limited to, BitTorrentby BitTorrent, Inc., when used with peer-to-peer messaging, provides amechanism for achieving a peer-to-peer IoT network. Examples ofdistributed file sharing usage comprise functions such as, but notlimited to, transfer of analytics reports, sharing content anddistributing software/firmware updates. Further, distributed filesharing can establish capability for an IoT device to maintain its owndata and thereby reduces the need for centralized infrastructure and theassociated costs of maintaining data of low-value IoT devices. It shouldbe noted that an IoT device life-span can surpass a centralizedinfrastructure owner. For example, a manufacturer of an IoT door lockmay go out of business and the central cloud interactions with thedevice could be disabled. While the IoT door lock could have a longlife, the loss of a centralized infrastructure could limit the door lockfunction. When an IoT device is responsible for its own data such as,but not limited to, identification data and service history, an IoTdevice can realize independence from a centralized infrastructure.

Autonomous IoT device coordination operates in the absence of acentralized controller acting as a broker and arbiter between IoTdevices. Embodiments of the present invention can comprise a consensusbased architecture to create trust in a “trustless” network, verifytransactions and manage roles and/or responsibilities of IoT devices ona peer-to-peer network. A “trustless” network can be defined as devicesinterconnected without referencing a central authentication authority.Further, consensus can be defined as a plurality of interconnecteddevices agreeing that a plurality of distributed data of interestmatches amongst the plurality of interconnected devices. Embodiments ofthe present invention can use technology such as, but not limited to,blockchain by bitcoin organization (bitcoin.org) as a decentralizationmechanism to achieve autonomous IoT device coordination and/orconsensus. Blockchain is an example technology that can establish trust,accountability and transparency when transacting and/or interacting withapplications. Blockchains can be stored on a plurality of computingdevices to eliminate reliance on a central authentication controlauthority. Blockchain can be described as a record and/or ledger ofdigital events where a blockchain can comprise one or more transactionalagreements between trading partners for a product and/or service thatcan be verified as authentic. Authenticity of a blockchain exchange isverified by consensus agreement among a collection of devices thatledger copies stored on those devices match.

Further, blockchain data can represent identifiable logical value (e.g.,digital currency, crypto-currency, etc.) that can be transferred betweencomputing devices, in exchange for goods and/or services. The ability toestablish trust through consensus (e.g., distributed ledger), enablesthe ability to perform a wide range of digital transactions that can betracked and traded without requiring a central point of control and canestablish the ability for IoT devices to operate autonomously. Examplesof autonomous IoT device coordination between IoT devices can compriseregistration, authentication of IoT devices, establishing rules ofengagement based on proximity and/or peer consensus (e.g., agreement),negotiating complex contracts and/or checklists between IoT devices andmechanizing digital currency for monetary value exchanges.

In embodiments of the present invention, different IoT devices canperform different functions based on their capability. For illustrativepurposes, ADEPT IoT devices are classified by three category types basedon degrees of functional capabilities. Functional capabilities can varybased on the type of function an IoT device is instrumented for and maybe classified as a hybrid of the three designated ADEPT peer types. TheADEPT peer types are identified as light peer, standard peer and peerexchange where each respective peer type can have increasing capabilityand/or functionality. The architecture of ADEPT can comprise custom andopen source protocols in any combination to achieve functionalitydescribed in embodiments of the present invention represented by theADEPT light peer, standard peer and peer exchange types. It should benoted that each ADEPT peer device can have capability to performself-diagnostics and/or transactional data processing based in IoTsensor input and connected device interchanges ranging in complexity.

In embodiments of the present invention, light peers can comprisedevices with low memory and storage capabilities. Some examples of ADEPTcapable light peers can comprise devices such as, but not limited to,Raspberry Pi by Raspberry Foundation, Beaglebone by Beaglebone.orgFoundation and Arduino board by Arduino LLC. Light peers can performmessaging, file sharing and comprise light wallets which have limitedcapability to store full blockchains and can rely on a trusted ADEPTpeer for more complex blockchain transactions (e.g., blockchainmining/verification, crypto-currency exchange).

In embodiments of the present invention, standard peers can be devicesthat have more memory and computing capabilities than light peers.Standard peers can store blockchain information for a limited durationand can perform blockchain transactions for light peers in an ADEPTpeer-to-peer network.

In embodiments of the present invention, peer exchanges can comprisedevices with significant computing and storage capabilities. Peerexchanges can comprise similar capability of standard peers and cancomprise a further capability of hosting marketplaces which can supportfunctions such as, but not limited to, payments, analytical solutions,demand supply matching and compliance. Peer exchanges can store a fullcopy of blockchains and perform “mining” and/or transaction verificationon the blockchains. It should be noted that in some embodiments of thepresent invention, a wallet (e.g., light wallet, optimized wallet andfull wallet) can comprise a plurality of blockchains and in otherembodiments of the present invention, one or more wallets can storeseparate data based on blockchain data type (e.g., wallets separated bycontract types and/or trading partners).

Embodiments of the present invention will now be described in detailwith reference to the figures. It should be noted that references in thespecification to “an exemplary embodiment,” “other embodiments,” etc.,indicate that the embodiment described may include a particular feature,structure, or characteristic, but every embodiment may not necessarilyinclude the particular feature, structure, or characteristic. Moreover,such phrases are not necessarily referring to the same embodiment.Further, when a particular feature, structure or characteristic isdescribed in connection with an embodiment, it is submitted that it iswithin the knowledge of one skilled in the art to affect such feature,structure or characteristic in connection with other embodiments whetheror not explicitly described.

FIG. 1 depicts a functional block diagram illustrating computingenvironment 100, in accordance with an embodiment of the presentinvention. Computing environment 100 comprises COMMUNICATION DEVICE 110,and COMPUTER SYSTEM 130, connected via NETWORK 140. COMMUNICATION DEVICE110 and COMPUTER SYSTEM 130 can be desktop computers, laptop computers,specialized computer servers, IoT devices or the like. It should benoted that IoT devices can be embedded in COMPUTER SYSTEM 130 (notdepicted) and/or COMMUNICATION DEVICE 110 or IoT devices can representCOMPUTER SYSTEM 130 and/or COMMUNICATION DEVICE 110 independently. Incertain embodiments, COMMUNICATION DEVICE 110 and COMPUTER SYSTEM 130represent computer systems utilizing clustered computers and componentsacting as a single pool of seamless resources via NETWORK 140. Forexample, such embodiments can be used in data center, cloud computing,storage area network (SAN), and network attached storage (NAS)applications. In general, COMMUNICATION DEVICE 110 and COMPUTER SYSTEM130 are representative of any electronic devices, or combination ofelectronic devices, capable of executing computer readable programinstructions, as described in detail with regard to FIG. 6.

In one embodiment of the present invention, COMPUTER SYSTEM 130 compriseUSER APPLICATION(S) 132. USER APPLICATION(S) 132 can be a plurality ofUSER APPLICATION(S) 132 within COMPUTER SYSTEM 130. USER APPLICATION(S)132 are applications that can perform functions such as, but not limitedto, send messages, receive messages and operate IoT devices. Inembodiments of the present invention, USER APPLICATION(S) 132 cancomprise any combination of commercial or custom devices and/or softwareproducts associated with actions such as, but not limited to, operating,maintaining and interacting with IoT devices. It should be noted thatUSER APPLICATION(S) 132 can represent central remote IOT controllers andcloud services where operations beyond a single peer-to-peer network canbe provided.

NETWORK 140 can be, for example, a local area network (LAN), a wide areanetwork (WAN) such as, but not limited to, the Internet and Bluetooth byBluetooth Special Interest Group (SIG), in any combination comprisingwired, wireless, or fiber optic connections. In general, NETWORK 140 canbe any combination of connections and protocols that can supportcommunications between COMMUNICATION DEVICE 110 and COMPUTER SYSTEM 130,in accordance with an embodiment of the present invention.

In one embodiment of the present invention, COMMUNICATION DEVICE 110comprises IoT DEVICE_L 112, IoT DEVICE_S 114 and IoT DEVICE_X 116.Correspondingly, IoT DEVICE_L 112 comprises ADEPT LIGHT PEER 118, IoTDEVICE_S 114 comprises ADEPT STANDARD PEER 120 and IoT DEVICE_X 116comprises ADEPT PEER EXCHANGE 122. ADEPT LIGHT PEER 118, ADEPT STANDARDPEER 120 and ADEPT PEER EXCHANGE 122 can provide progressively greaterfunction based on IoT device properties such as, but not limited to,processing capacity, storage capacity and application/functionalrequirements.

In one embodiment of the present invention, IoT DEVICE_L 112, IoTDEVICE_S 114 and IoT DEVICE_X 116 can be a plurality of IoT DEVICE_L(S)112, IoT DEVICE_S(S) 114 and IoT DEVICE_X(S) 116 respectively. IoTDEVICE_L 112, IoT DEVICE_S 114 and IoT DEVICE_X 116 can be a pluralityof components of COMMUNICATION DEVICE 110 and likewise, IoT DEVICE_L112, IoT DEVICE_S 114 and IoT DEVICE_X 116 can be represented asCOMMUNICATION DEVICE 110 in a stand-alone environment. IoT DEVICE_L 112,IoT DEVICE_S 114 and IoT DEVICE_X 116 can represent IoT devices that cancomprise a plurality of sensors (not shown) and provide connectivitythat can detect and respond to environmental and/or computer initiatedevents (e.g., telemetry). IoT DEVICE_L 112, IoT DEVICE_114 and IoTDEVICE_X 116 can comprise any combination of commercial or customdevices and/or software products associated with IoT devices. It shouldbe noted that IoT devices connectivity can vary over time as IoT devicescan attach/detach themselves to/from a network as needed. For example,an alarm system IoT device can connect to a network when a user enablesa security system or a smoke-detector IoT device can connect to anetwork when predetermined threshold conditions are detected (e.g., weakbattery alert).

In one embodiment of the present invention ADEPT LIGHT PEER 118, ADEPTSTANDARD PEER 120 and ADEPT PEER EXCHANGE 122 can comprise functionssuch as, but not limited to, autonomous interconnection to a pluralityof ADEPT peers, transfer data/files, perform messaging, storeinformation and provide consensus based device coordination. ADEPT LIGHTPEER 118, ADEPT STANDARD PEER 120 and ADEPT PEER EXCHANGE 122 cancomprise any combination of commercial or custom devices and/or softwareproducts associated with IoT device operation and more particularly inoperating an ADEPT based architecture.

FIG. 2 depicts an IoT ADEPT peer autonomous device architecture, inaccordance with an embodiment of the present invention. ADEPTarchitecture 200 further decomposes to ADEPT LIGHT PEER 118, ADEPTSTANDARD PEER 120 and ADEPT PEER EXCHANGE 122 where each peer comprisesMESSAGING 204 and FILE TRANSFER 206.

In one embodiment of the present invention ADEPT LIGHT PEER 118, ADEPTSTANDARD PEER 120 and ADEPT PEER EXCHANGE 122 further comprise LIGHTWALLET 202A, OPTIMIZED WALLET 202B and FULL WALLET 202C respectively.LIGHT WALLET 202A, OPTIMIZED WALLET 202B and FULL WALLET 202C canprocess and store distributed transactions. Transaction processing canbe performed by technologies such as, but not limited to, blockchain.Blockchain can be used to create trust between devices, allow data to bestored on different devices while tracking the relationship betweendifferent owners/users of the data and establish contract exchangebetween trading partners. It should be noted that device and/or ADEPToperation data such as, but not limited to, device responsibilities,device relationships, autonomous device coordination rules, deviceservice history and the device consensus service contracts can be storedin ADEPT peer wallets and/or other memory locations available to theADEPT peers. It should be noted that stored service history can becomprise information such as, but not limited to, repair actions,warranty/contract status, service action statistics and partsreplacement statistics.

In one embodiment of the present invention, LIGHT WALLET 202A can beused to track relationships and agreements that can be negotiated byADEPT LIGHT PEER 118 with other ADEPT IoT devices, COMMUNICATION DEVICE110 and/or COMPUTER SYSTEM 130. For example, LIGHT WALLET 202A can storeblockchain(s) and/or portions of blockchain(s) and contracts associatedwith devices identified on blockchain(s). Further, LIGHT WALLET 202A canstore referential information toward a peer-to-peer connected ADEPTSTANDARD PEER 120 and/or ADEPT PEER EXCHANGE 122 where associatedblockchain data can be stored when LIGHT WALLET 202A has limited storagespace. It should be noted that authorization of ADEPT IoT devices can beexecuted on a shared registry such as, but not limited to, blockchain.For example, authorizaton can be executed between a user and a deviceand between two devices autonomously or with added user consent asidentified on the blockchain. For example, the authorizationcapabilities of blockchain can provide a smartphone with a secure methodof communication with a door lock and/or a user could authorize someoneelse to communicate with the door lock. ADEPT IoT authenicatedrelationships could be stored on the lock's IoT device and/or thesmartphone which can communicate with each other as needed to ensure theauthorized people have access to a secure area.

In one embodiment of the present invention, OPTIMIZED WALLET 202Bcomprises similar capabilities as LIGHT WALLET 202A and can be used totrack relationships and agreements that can be negotiated by ADEPTSTANDARD PEER 120 relationships with other ADEPT IoT devices,COMMUNICATION DEVICE 110 and/or COMPUTER SYSTEM 130. For example,OPTIMIZED WALLET 202B can store blockchain(s) and contracts with adevice(s) identified on blockchain(s).

In one embodiment of the present invention, FULL WALLET 202C comprisessimilar capabilities as OPTIMIZED WALLET 202B and can be used to trackrelationships and agreements that can be negotiated by ADEPT PEEREXCHANGE 122 relationships with other ADEPT IoT devices, COMMUNICATIONDEVICE 110 and/or COMPUTER SYSTEM 130. For example, FULL WALLET 202C canstore blockchain(s) and contracts with device(s) identified onblockchain(s). Further, FULL WALLET 202C can store data for otherservices negotiated/bartered by ADEPT PEER EXCHANGE 122 such as, but notlimited to, marketplace transactions. For example, ADEPT PEER EXCHANGE122 could negotiate energy allocations with a Heating, Ventilation andAir Conditioning (HVAC) system to “buy” and “sell” energy credits.

In one embodiment of the present invention MESSAGING 204, can be aplurality of MESSAGING(S) 204 within ADEPT LIGHT PEER 118, ADEPTSTANDARD PEER 120 and ADEPT PEER EXCHANGE 122. MESSAGING 204 can enablecommunication in an understandable format/protocol between a pluralityof COMMUNICATION DEVICE 110 and COMPUTER SYSTEM 130. ADEPT LIGHT PEER118, ADEPT STANDARD PEER 120 and ADEPT PEER EXCHANGE 122 can operateMESSAGING 204 using a protocol such as, but not limited to, telehash byTelehash Organization (i.e., telehash.org). In embodiments of thepresent invention, MESSAGING 204 can comprise any combination ofcommercial or custom devices and/or software products associated withenabling a peer-to-peer messaging protocol in a “trustless” consensusbased network to share distributed information. It should be noted thatMESSAGING 204 can provide secure end-to-end encryption within an ADEPTpeer-to-peer network.

In one embodiment of the present invention FILE TRANSFER 206, can enableADEPT LIGHT PEER 118, ADEPT STANDARD PEER 120 and ADEPT PEER EXCHANGE122 with the ability to transfer data/files within the ADEPT peernetwork. Embodiments of the present invention can transfer blocks ofdata among a plurality of IoT devices using technologies such as, butnot limited to, BitTorrent. It should be noted, while IoT devices canjoin and leave a network periodically, a distributed file sharingtechnology can successfully enable decentralized autonomous operations.It should be further noted that factors such as, but not limited to,storage capacity, IoT device processing speed/power can vary among ADEPTLIGHT PEER 118, ADEPT STANDARD PEER 120 and ADEPT PEER EXCHANGE 122 suchthat distributed file sharing among many IoT devices in a peer-to-peernetwork can be advantageous.

ADEPT STANDARD PEER 120 and ADEPT PEER EXCHANGE 122 further compriseAUTONOMOUS DEVICE COORD 208, DEVICE LEVEL ANALYTICS 210 and TRANSACTIONVERIFY 212.

In one embodiment of the present invention, AUTONOMOUS DEVICE COORD 208represents the ability of ADEPT STANDARD PEER 120 and ADEPT PEEREXCHANGE 122 to operate and manage functions such as, but not limitedto, communication, cooperation and file sharing with connected devicesin an ADEPT peer-to-peer network. It should be noted that as ADEPT LIGHTPEER 118, ADEPT STANDARD PEER 120 and ADEPT PEER EXCHANGE 122participate in a decentralized peer-to-peer network, the ADEPT IoTdevices, based on their capabilities, can forward transactions towardother ADEPT IoT devices on behalf of transaction originating ADEPT IoTdevices in the peer-to-peer network. It should be further noted thatAUTONOMOUS DEVICE COORD 208 can detect and interact with networkconnected trading partners to enable an ADEPT network interchange withcontracted service providers. For example, a service provider (e.g.,trading partner) can be identified on a service contract (e.g.,blockchain party). If a need to exchange information with the serviceprovider is determined, then the ADEPT network can establish aconnection beyond the peer-to-peer ADEPT network (e.g., Internetconnection) to transact and perform consensus based value exchanges.

In one embodiment of the present invention, DEVICE LEVEL ANALYTICS 210,represents the ability of ADEPT STANDARD PEER 120 and ADEPT PEEREXCHANGE 122 to perform data analytics to determine and manage dataavailable within an ADEPT peer-to-peer network. DEVICE LEVEL ANALYTICS210 can analyze data (e.g., diagnostic input) from various sources tomake autonomous decisions such as, but not limited to, determining theneed for a resource, offering computational resources to another IoTdevice and acting on sensor information shared within the peer-to-peernetwork. For example, an appliance IoT can receive diagnostic input todetect water flow rate change below a predetermined threshold. The flowrate event detection could indicate that a water filter needsreplacement however, DEVICE LEVEL ANALYTICS 210 can compare partsreplacement history stored on the ADEPT device and/or stored on apeer-to-peer networked device to determine if a current and/or pastfilter replacement history conforms to a predetermined life span. If afilter replacement schedule comparison indicates a premature failure,additional diagnostics can be executed to determine if other partfailure(s) may be contributing to the sensed reduced water flow event.Based on DEVICE LEVEL ANALYTICS 210 results, autonomous actions can beexecuted by the ADEPT peer(s) to initiate service self-service. Itshould be noted that analytic data and reports can be transferred withFILE TRANSFER 206 among an ADEPT peer-to-peer network and/or networkconnected service provider(s). It should be further noted thatdiagnostic input can be received by an ADEPT device from sources suchas, but not limited to, the ADEPT device attached sensor input, theADEPT device analytic results actions, connected ADEPT device(s)analytic result actions and connected ADEPT device(s) sensor input.

In one embodiment of the present invention, TRANSACTION VERIFY 212, canprovide consensus based functions such as, but not limited to, validateauthorization and service requests within the ADEPT peer-to-peer networkto create and accept permissions and/or contract for services and setroles and/or responsibilities between IoT devices and/or networkconnected service provider(s). For example, an ADEPT peer can request apart from a service provider. With reference to an ADEPT contractbetween an ADEPT enabled device and a service provider, the partsrequest transaction can be verified as authentic for both requesting andsupplying parties when a plurality of ADEPT networked peers confirmblockchain match (e.g., ledger consensus).

In one embodiment of the present invention, ADEPT PEER EXCHANGE 122further comprises MARKETPLACE 214. With MARKETPLACE 214, ADEPT PEEREXCHANGE 122 can negotiate service exchanges with networked devices,resources and/or network connected service provider(s). For example,MARKETPLACE 214 can be used to barter with other IoT devices for energyusage or in another example, MARKETPLACE 214 can buy/sell processingcapacity to perform a software update or display advertisements. In yetanother example, MARKETPLACE 214 can connect with service providers toinitiate creation of new service contracts when a need for a consensusservice contract is determined. An ADEPT peer can create servicecontract offers and send service contract offers toward serviceproviders. Service providers can determine if they accept receivedcontract offers and can send one or more contract acceptance toward therequesting ADEPT peer. Upon receipt of service contract acceptances,consensus service contracts can be created (e.g., blockchain) by arequesting ADEPT peer and shared among the ADEPT peer network to enabletrusted (e.g., consensus based) exchange of services and/or parts ordersas ADEPT peer device(s) operate. It should be noted that determinationof the need for a consensus contract can be identified by events suchas, but not limited to, activating an ADEPT peer device (e.g., warrantyactivation), predetermined ADEPT peer device(s) service records/profileand identified user established agreements (e.g., product serviceagreement) sent toward ADEPT peer device(s).

FIG. 3 illustrates a flowchart depicting ADEPT peer self-servicinginteractions, in accordance with an embodiment of the present invention.Flow diagram 300 ADEPT peer self-service processing can be a continuousprocess operated by an ADEPT IoT device participating in an ADEPTpeer-to-peer network to sense and respond to ADEPT peer self-servicinginteractions.

In operation SENSE PEER 302, an ADEPT IoT device (e.g., ADEPT LIGHT PEER118, ADEPT STANDARD PEER 120 and ADEPT PEER EXCHANGE 122) can determineif at least one of a plurality of other ADEPT LIGHT PEER 118, ADEPTSTANDARD PEER 120 and ADEPT PEER EXCHANGE 122 are available toestablish/extend a peer-to-peer network. A peer list can be created andmaintained by each ADEPT IoT device as other ADEPT IoT devicesjoin/leave the peer-to-peer network. It should be noted that the peerlist can be stored in ADEPT IoT devices memory and/or respective LIGHTWALLET 202A, OPTIMIZED WALLET 202B and FULL WALLET 202C to identifywhich ADEPT IoT devices are in range and what peer-to-peer connectionsare established. It should be further noted that the peer list enablesADEPT IoT devices to differentiate between known and unknown peers in apeer-to-peer network where the relationships between peer devices can beclassified by terms such as, but not limited to, trusted, semi-trustedand trustless. The peer list classification terms can be based on ADEPTIoT device predetermined rules.

In operation INTERCONNECT PEER 304, the ADEPT IoT device can sendmessages toward other peers and/or can receive messages from other peersto join a peer-to-peer network. A level of trust can be established withanother ADEPT IoT device to create a peer-to-peer networkinterconnection between ADEPT peers by using technologies such as, butnot limited to, blockchain. With blockchain, ADEPT peers can establishauthenticated and/or encrypted connectivity with trusted, semi-trustedand trustless peer-to-peer devices.

In operation FILE TRANSFER 306, authenticated data and/or transactionscan be sent and/or received between peers. Examples of data and/ortransactions can comprise code updates, reports, diagnostics and servicehistory based on blockchain authentication and/or consensus.

In operation SENSE EVENT 308, an event can be received from a peerand/or sensor within the IoT network. Examples of events that can occurcan be a sensor meeting a threshold value (e.g., humidity levelexceeded), instrumented part fails (e.g., filter is plugged, valve failsto close, etc.), a device needs attention (e.g., power loss), periodicalert (e.g., diagnostics report due), environmental event (e.g., smokedetected), user instruction message (e.g., parameter change) andresponsibility negotiation (e.g., marketplace request).

Based on operation SENSE EVENT 308, event identification, operationACTION NEEDED 310, determines if action is needed to be taken by theADEPT IoT device. Action determination can be based on a range ofactions the IoT device is designed to manage and if the IoT device iscapable of performing the action. In the condition where operationACTION NEEDED 310 determines no action is needed, then the flow ends. Anaction decision can be determined based on analytic processing within anADEPT peer onboard analytics and/or received from one or more ADEPT peeranalytics results. In the condition where operation ACTION NEEDED 310determines action is needed, then the flow proceeds to operation PROCESSEVENT 312.

In operation PROCESS EVENT 312, an event can be processed by an IoTdevice taking action based on the responsibilities of the ADEPT IoTdevice and/or based on ADEPT peer relationships. An ADEPT IoT device canperform actions, such as, but not limited to, message handling, messagegeneration, consensus determination participation, peer informationmanagement, contract creation, contract execution, contract management,file management, external API invocation and triggering other events. Anexample of IoT event processing can comprise actions to negotiateservice (e.g., contract creation) from other devices in the peer-to-peernetwork. For example, ADEPT LIGHT PEER 118 may need a firmware updateand ADEPT LIGHT PEER 118 associated IoT DEVICE_L 112 has insufficientfree memory to retain temporary install files. ADEPT LIGHT PEER 118could negotiate (e.g., contract) with a connected ADEPT PEER EXCHANGE122 to store data (e.g., file transfer) on an associated IoT DEVICE_X116 in order to complete the update.

In operation SERVICE NEEDED 314, an operation ACTION NEEDED 310 cancomprise a need for actions to be managed by trading partners beyond anADEPT peer-to-peer network (e.g., service order send toward serviceprovider). For example, parts and/or service may be needed such as, butnot limited to, a replacement part, consumable part and repair call. Ifoperation SERVICE NEEDED 314 is no, then processing proceeds towardoperation SENSE EVENT 308 to receive a next event, otherwise operationcontinues toward operation PROCESS SERVICE 316.

In operation PROCESS SERVICE 316, a connection can be made between theADEPT peer-to-peer network and a service provider(s) to deliverservice(s) and/or part(s). Existing contracts can be referenced and/ornew contacts can be initiated based on predetermined service providerrules received by and/or stored in an ADEPT peer. Service providercommunication can provide a transaction capability such as, but notlimited to, consensus based contract, order, receipt, delivery anddiagnostic information exchange. It should be noted that ADEPT deviceparticipating in an ADEPT peer-to-peer network can vary in capabilityand connectivity with service providers. For example, it is possiblethat an ADEPT LIGHT PEER 118 can determine a service part need andnegotiate with a connected ADEPT PEER EXCHANGE 122 to share serviceordering and/or service contract negotiation activities between theADEPT LIGHT PEER 118 and a service provider to deliver a service(s).When operation SERVICE NEEDED 314 is complete, processing proceedstoward operation SENSE EVENT 308 to receive a next event.

FIG. 4 depicts a sample implementation of an IoT ADEPT peer deviceoperation, in accordance with an embodiment of the present invention.ADEPT sample operation 400 comprises ADEPT WASHER 402, DETERGENT CHECK404, ENERGY ALERT 406, SERVICE CHECK 408 and USER MESSAGING 410. Itshould be noted that ADEPT sample operation 400, refers to enablingtechnologies such as, but not limited to, blockchain for illustrationpurposes.

In one embodiment of the present invention, ADEPT WASHER 402 can beADEPT IoT enabled washing machine. In an example, ADEPT WASHER 402 candetermine when detergent levels are low based on sensors and/or messagessent toward ADEPT WASHER 402. ADEPT WASHER 402 can send messages towardUSER MESSAGING 410 to notify a user to re-stock detergent and/or USERMESSAGING 410 can send messages toward DETERGENT CHECK 404 wheredetergent can be ordered from a service provider. Billing/payment can bemade with authenticated information on a blockchain exchanged betweenADEPT WASHER 402 and a service provider. The authenticated informationcan comprise information such as, but not limited to, device ID,crypto-currency exchange and contract ID. The service provider can alsosend confirmations such as, but not limited to, order acknowledgment,shipping details and billing information toward ADEPT WASHER 402 and/ora user.

In one embodiment of the present invention, ENERGY ALERT 406 can operatein an energy managed environment where peak energy usage may begoverned. In this example, ADEPT WASHER 402 can negotiate/barter energyusage with an HVAC system. After successful negotiation on a blockchain,HVAC can limit energy demand (e.g., delay heat, air conditioning) whileADEPT WASHER 402 operates. Conversely, ADEPT WASHER 402 could pauseperiodically between wash cycles based on autonomous coordination withthe HVAC system.

In one embodiment of the present invention, SERVICE CHECK 408 operateswhen ADEPT WASHER 402 determines that service may be needed. Forexample, a filter may be plugged and ADEPT WASHER 402 can determinewater flow has diminished. ADEPT WASHER 402 can send messages towardUSER MESSAGING 410 to notify a user that an event has occurred and/orSERVICE CHECK 408 to send a service request toward a service vendor. Theservice request can comprise information such as, but not limited to,part number failing, machine repair history, error codes, softwareversion and analytic reports. The service vendor could determine actionsto take based on information received and confirm actions to take suchas, but not limited to, dispatch a service technician and/or parts. Itshould be noted that machine repair history is one example of ADEPT IoTdevice having responsibility of its own data in a peer-to-peerdistributed architecture. It should be further noted that USER MESSAGING410 can participate in communication with ADEPT WASHER 402, DETERGENTCHECK 404, ENERGY ALERT 406, SERVICE CHECK 408 based on a plurality ofimplementations of embodiments of the present invention.

FIG. 5 depicts transactions in a sample digital value exchange scenarioof an IoT ADEPT peer device, in accordance with an embodiment of thepresent invention. Sample ADEPT transaction exchange 500 depictscommunication self-servicing interactions that can occur during an ADEPTWASHER 402 sensed filter failure. It should be noted that ADEPTtransaction exchange 500, refers to enabling technologies such as, butnot limited to, blockchain for illustration purposes.

Item ADEPT WASHER 402 comprises item Washer Sensor 502 and item WasherAnalytics 504 that can be functional components of an ADEPT IoT device.Item Service Provider 506 depicts a seller of goods and service (e.g.,washer detergent). Item Owner 510 depicts a communications device thatreceives messages representing an owner/user interested in theautonomous operation of ADEPT WASHER 402.

Item Transaction Consensus 508 depicts a distributed method to verifyand record value (e.g., digital currency) exchange between ADEPT peer(s)and/or other partners (e.g., item Service Provider 506) identified on ablockchain. Blockchain can represent item Transaction Consensus 508where blockchains (e.g., ledgers) are maintained as value is exchangedamong trading partners (e.g., ADEPT peer(s), item Service Provider 506).

Item ESTABLISH CONTRACT 512, item ANALYTICS 514 and item FILTER RE-ORDER516 represent groupings of transactions comprising communicationexchanges that can occur while operating SERVICE CHECK 408.

Item ESTABLISH CONTRACT 512 can be autonomously performed between ADEPTWASHER 402 and item Service Provider 506 where an agreement can benegotiated between trading partners. When a need for a part and/orservice from a Service Provider is determined (e.g., item ANALYTICS514), ‘Find Provider’ can search information sources such as, but notlimited to, existing consensus service contracts (e.g., warranty, parts,service) and authorized service providers can be searched to satisfy aparts and/or service need. A consensus service contract can beidentified as a contract (e.g., blockchain) structure identifying anagreement between a consumer (e.g., ADEPT WASHER 402) and a serviceprovider based on terms to deliver parts and/or service. The consensusservice contracts can comprise data such as, but not limited to, serviceprovider identifiers, service identifiers, contract terms and contractvalues. Contract terms can comprise attributes such as, but not limitedto, replaceable parts list, service hours based on contract type andavailable repair task identifiers. Contract values can comprise datasuch as, but not limited to, part values, part useful life, part meantime between failure (MTBF), part identification substitution rules andaverage repair time per repair task.

If a Service Provider 506 is found, a search is conducted to determineif an existing contract (e.g., warranty, service contract, etc.) existsfor the parts and/or service need. If a service provider is not found, auser can be notified (e.g., USER MESSAGING 410) of the parts and/orservice need (not depicted). If a contract is not found in ‘FindContract’, a new contract can be created. In the example, a contract canbe created for a replacement filter where ‘Create Contract’ messagingcan comprise attributes such as, but not limited to, contractidentifier, value, terms and conditions and can be shared between ADEPTWASHER 402 and item Service Provider 506. With an agreeable contractdefined, ADEPT WASHER 402 can send ‘Sign Contract_1’ (e.g., servicecontract offer) transaction toward item Transaction Consensus 508 toregister authorization of the detergent contract. Likewise, item ServiceProvider 506 can send a corresponding ‘Sign Contract_2’ (e.g., servicecontract acceptance) transactions toward item Transaction Consensus 508to complete authorization of the filter contract.

Item ANALYTICS 514 can comprise function that is executing on an IoTdevice and/or interfacing computing device with ADEPT WASHER 402. Forexample, item ANALYTICS 514 comprises a ‘Sense Filter Status’ messagethat can be sent toward item Washer Analytics 504 where the currentwater flow rate in ADEPT WASHER 402 is sensed. Item ANALYTICS 514 canprocess received ‘Sense Filter Status’ message and based on itemANALYTICS 514, predetermined decision rules can identify a need for areplacement filter. If a need to replacement filter exists, itemANALYTICS 514 can send ‘Replace Filter’ message toward ADEPT WASHER 402to initiate item FILTER RE-ORDER 516 process.

Item FILTER RE-ORDER 516 can operate autonomously with ADEPT WASHER 402.For example, based on an item ANALYTICS 514 triggering event, ‘ReplaceFilter’, ADEPT WASHER 402 can send a filter request (i.e., ‘FilterReq.’) toward the service provider (e.g., item Service Provider 506).The filter request can comprise information such as, but not limited to,ADEPT Washer identifier and contract reference established from itemESTABLISH CONTRACT 512. A corresponding ‘User Notify Filter Request’message can be sent toward item Owner 510 by ADEPT WASHER 402.Additionally, ADEPT WASHER 402 can send ‘Contract (Payment) for Filter’(e.g., digital currency) toward item Transaction Consensus 508, where anexample blockchain technology can be used, to authenticate, byconsensus, ADEPT WASHER 402 (e.g., buying party) transaction for paymenttoward item Service Provider 506. It should be noted that a contractpayment can be a value exchange for the service provider for recordspurpose. For example, a service part covered under warranty would not bea monetary exchange however the Service Provider 506 can use the valueexchange as a method to monitor Service Provider 506 cost ofmaintenance. Correspondingly, item Transaction Consensus 508 can send‘Receive Payment’ transaction toward item Service Provider 506 tocollect payment for the determent associated to the contract (e.g., itemESTABLISH CONTRACT 512). Further, item Service Provider 506 can send‘Order Accept’ and ‘Delivery Note’ toward ADEPT WASHER 402 toacknowledge that the filter request can be satisfied and/or whenreplenishment will be complete. Lastly, ADEPT WASHER 402 can send ‘UserNotify Filter Delivery’ message toward Item Owner 510 as completionnotification of the autonomous filter replenishment operation. It shouldbe noted that Item FILTER RE-ORDER 516 is an example of a replacementpart order and a request for service and/or dispatch of a repairtechnician can follow a similar process flow.

FIG. 6 depicts a block diagram of components of the server and/or thecomputing device, in accordance with an embodiment of the presentinvention. It should be appreciated that FIG. 6 provides only anillustration of one implementation and does not imply any limitationswith regard to the environments in which different embodiments may beimplemented. Many modifications to the depicted environment may be made.

Computer system 600 includes communications fabric 602, which providescommunications between computer processor(s) 604, memory 606, persistentstorage 608, communications unit 610, and input/output (I/O)interface(s) 612. Communications fabric 602 can be implemented with anyarchitecture designed for passing data and/or control informationbetween processors (such as, microprocessors, communications and networkprocessors, etc.), system memory, peripheral devices, and any otherhardware components within a system. For example, communications fabric602 can be implemented with one or more buses.

Computer system 600 includes processors 604, cache 616, memory 606,persistent storage 608, communications unit 610, input/output (I/O)interface(s) 612 and communications fabric 602. Communications fabric602 provides communications between cache 616, memory 606, persistentstorage 608, communications unit 610, and input/output (I/O)interface(s) 612. Communications fabric 602 can be implemented with anyarchitecture designed for passing data and/or control informationbetween processors (such as, microprocessors, communications and networkprocessors, etc.), system memory, peripheral devices, and any otherhardware components within a system. For example, communications fabric602 can be implemented with one or more buses or a crossbar switch.

Memory 606 and persistent storage 608 are computer readable storagemedia. In this embodiment, memory 606 includes random access memory(RAM). In general, memory 606 can include any suitable volatile ornon-volatile computer readable storage media. Cache 616 is a fast memorythat enhances the performance of processors 604 by holding recentlyaccessed data, and data near recently accessed data, from memory 606.

Program instructions and data used to practice embodiments of thepresent invention may be stored in persistent storage 608 and in memory606 for execution by one or more of the respective processors 604 viacache 616. In an embodiment, persistent storage 608 includes a magnetichard disk drive. Alternatively, or in addition to a magnetic hard diskdrive, persistent storage 608 can include a solid state hard drive, asemiconductor storage device, read-only memory (ROM), erasableprogrammable read-only memory (EPROM), flash memory, or any othercomputer readable storage media that is capable of storing programinstructions or digital information.

The media used by persistent storage 608 may also be removable. Forexample, a removable hard drive may be used for persistent storage 608.Other examples include optical and magnetic disks, thumb drives, andsmart cards that are inserted into a drive for transfer onto anothercomputer readable storage medium that is also part of persistent storage608.

Communications unit 610, in these examples, provides for communicationswith other data processing systems or devices. In these examples,communications unit 610 includes one or more network interface cards.Communications unit 610 may provide communications through the use ofeither or both physical and wireless communications links.

Program instructions and data used to practice embodiments of thepresent invention may be downloaded to persistent storage 608 throughcommunications unit 610.

I/O interface(s) 612 allows for input and output of data with otherdevices that may be connected to each computer system. For example, I/Ointerface 612 may provide a connection to external devices 618 such as,a keyboard, keypad, a touch screen, and/or some other suitable inputdevice. External devices 618 can also include portable computer readablestorage media such as, for example, thumb drives, portable optical ormagnetic disks, and memory cards. Software and data used to practiceembodiments of the present invention can be stored on such portablecomputer readable storage media and can be loaded onto persistentstorage 608 via I/O interface(s) 612. I/O interface(s) 612 also connectto display 620.

Display 620 provides a mechanism to display data to a user and may be,for example, a computer monitor.

The programs described herein are identified based upon the applicationfor which they are implemented in a specific embodiment of theinvention. However, it should be appreciated that any particular programnomenclature herein is used merely for convenience, and thus theinvention should not be limited to use solely in any specificapplication identified and/or implied by such nomenclature.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such as,punch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as, radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as, Smalltalk, C++ or the like, andconventional procedural programming languages, such as, the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the invention.The terminology used herein was chosen to best explain the principles ofthe embodiment, the practical application or technical improvement overtechnologies found in the marketplace, or to enable others of ordinaryskill in the art to understand the embodiments disclosed herein.

What is claimed is:
 1. A method, for autonomous self-servicing ofdecentralized peer-to-peer devices in an autonomous decentralizedpeer-to-peer telemetry (ADEPT) environment, the method comprising:connecting, by a first ADEPT peer, to one or more ADEPT peers based onpeer consensus; determining, by the first ADEPT peer, one or moreservice needs based on receiving one or more diagnostic inputs;identifying, by the first ADEPT peer, one or more service providersbased on one or more consensus service contracts associated to the oneor more service needs; creating, by the first ADEPT peer, one or moreservice orders based on the one or more service providers; andoutputting, by the first ADEPT peer, the one or more service orders tothe one or more service providers based on the one or more consensusservice contracts.
 2. The method of claim 1, wherein the one or moreconsensus service contracts are created by: sending, by the first ADEPTpeer, one or more service contract offers associated to the one or moreservice providers; receiving, by the first ADEPT peer, one or moreservice contract acceptances associated to the one or more servicecontract offers; and outputting, by the first ADEPT peer, the one ormore consensus service contracts toward the one or more ADEPT peers. 3.The method of claim 2 wherein the one or more service contract offersare based on activating the first ADEPT peer device, predetermined thefirst ADEPT peer device service records, predetermined ADEPT peer deviceservice profile and user established agreements.
 4. The method of claim1 wherein the one or more diagnostic inputs comprise at least one of oneor more sensor input, the first ADEPT peer analytic results actions, theone or more ADEPT peer analytic result actions and the one or more ADEPTpeer sensor input.
 5. The method of claim 1, wherein the one or moreADEPT peers, comprises one or more wallets comprising at least one ofone or more device responsibilities, one or more device relationships,one or more autonomous device coordination, one or more service historyand the one or more consensus service contracts.
 6. The method of claim1, wherein the one or more consensus service contracts comprise at leastone of one or more service provider identifiers, one or more serviceidentifiers, one or more contract terms and one or more contract values.7. The method of claim 5 wherein the one or more service historycomprises at least one of one or more repair actions, one or morecontract status, one or more service action statistics and one or moreparts replacement statistics.
 8. A computer program product, forautonomous self-servicing of decentralized peer-to-peer devices in anautonomous decentralized peer-to-peer telemetry (ADEPT) environment, thecomputer program product comprising: one or more computer readablestorage media and program instructions stored on the one or morecomputer readable storage media, the program instructions comprising:program instructions to, connect, by a first ADEPT peer, to one or moreADEPT peers based on peer consensus; program instructions to, determine,by the first ADEPT peer, one or more service needs based on receivingone or more diagnostic inputs; program instructions to, identify, by thefirst ADEPT peer, one or more service providers based on one or moreconsensus service contracts associated to the one or more service needs;program instructions to, create, by the first ADEPT peer, one or moreservice orders based on the one or more service providers; and programinstructions to, output, by the first ADEPT peer, the one or moreservice orders to one or more service providers based on the one or moreconsensus service contracts.
 9. The computer program product of claim 8,wherein the one or more consensus service contracts are created by:program instructions to, send, by the first ADEPT peer, one or moreservice contract offers associated to the one or more service providers;program instructions to, receive, by the first ADEPT peer, one or moreservice contract acceptances associated to the one or more servicecontract offers; and program instructions to, output, by the first ADEPTpeer, the one or more consensus service contracts toward the one or moreADEPT peers.
 10. The computer program product of claim 9 wherein the oneor more service contract offers are based on activating the first ADEPTpeer device, predetermined the first ADEPT peer device service records,predetermined ADEPT peer device service profile and user establishedagreements.
 11. The computer program product of claim 8 wherein the oneor more diagnostic inputs comprise at least one of one or more sensorinput, the first ADEPT peer analytic results actions, the one or moreADEPT peer analytic result actions and the one or more ADEPT peer sensorinput.
 12. The computer program product of claim 8, wherein the one ormore ADEPT peers, comprises one or more wallets comprising at least oneof one or more device responsibilities, one or more devicerelationships, one or more autonomous device coordination, one or moreservice history and the one or more consensus service contracts.
 13. Thecomputer program product of claim 8, wherein the one or more consensusservice contracts comprise at least one of one or more service provideridentifiers, one or more service identifiers, one or more contract termsand one or more contract values.
 14. The computer program product ofclaim 12, wherein the one or more service history comprises at least oneof one or more repair actions, one or more contract status, one or moreservice action statistics and one or more parts replacement statistics.15. A computer system, for autonomous self-servicing of decentralizedpeer-to-peer devices in an autonomous decentralized peer-to-peertelemetry (ADEPT) environment, the computer system comprising: one ormore computer processors; one or more computer readable storage media;program instructions stored on the one or more computer readable storagemedia for execution by at least one of the one or more computerprocessors, the program instructions comprising: program instructionsto, connect, by a first ADEPT peer, to one or more ADEPT peers based onpeer consensus; program instructions to, determine, by the first ADEPTpeer, one or more service needs based on receiving one or morediagnostic inputs; program instructions to, identify, by the first ADEPTpeer, one or more service providers based on one or more consensusservice contracts associated to the one or more service needs; programinstructions to, create, by the first ADEPT peer, one or more serviceorders based on the one or more service providers; and programinstructions to, output, by the first ADEPT peer, the one or moreservice orders to one or more service providers based on the one or moreconsensus service contracts.
 16. The computer system of claim 15,wherein the one or more consensus service contracts are created by:program instructions to, send, by the first ADEPT peer, one or moreservice contract offers associated to the one or more service providers;program instructions to, receive, by the first ADEPT peer, one or moreservice contract acceptances associated to the one or more servicecontract offers; and program instructions to, output, by the first ADEPTpeer, the one or more consensus service contracts toward the one or moreADEPT peers.
 17. The computer system of claim 16 wherein the one or moreservice contract offers are based on activating the first ADEPT peerdevice, predetermined the first ADEPT peer device service records,predetermined ADEPT peer device service profile and user establishedagreements.
 18. The computer system of claim 15 wherein the one or morediagnostic inputs comprise at least one of one or more sensor input, thefirst ADEPT peer analytic results actions, the one or more ADEPT peeranalytic result actions and the one or more ADEPT peer sensor input. 19.The computer system of claim 15, wherein the one or more ADEPT peers,comprises one or more wallets comprising at least one of one or moredevice responsibilities, one or more device relationships, one or moreautonomous device coordination, one or more service history and the oneor more consensus service contracts.
 20. The computer system of claim15, wherein the one or more consensus service contracts comprise atleast one of one or more service provider identifiers, one or moreservice identifiers, one or more contract terms and one or more contractvalues.